Hello lovely humans,

nyc just published its new version 6.6.0.

This version is covered by your current version range and after updating it in your project the build went from success to failure.

As nyc is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴

The new version differs by 14 commits .

• b9a3023 chore(release): 6.6.0
• ea028b9 feat: add "instrument" option as alternative to specifying noop instrumenter (#278)
• 9680306 chore(release): 6.5.1
• 344af40 chore(package): update signal-exit to version 3.0.0 (#277)
• 1b9e4a8 fix: upgrade foreground-child dependency (#276)
• 8df87dc docs(badge): add branch to Travis badge
• b1fe746 chore(release): 6.5.0
• 9fd2295 feat: make __coverage__ the default approach we advocate for ES2015 coverage (#268)
• 8164b5e chore(package): update is-windows to version 0.2.0 (#267)
• df591f4 fix: Update AppVeyor config with ~faster npm install (#252)
• 53e683b tests: test against more relevant versions of node on Travis (#251)
• a20d03d fix: cleanup dependencies (#254)
• 0838a0e fix: discard more bad source map positions (#255)
• 0a78ad5 chore(package): update lodash to version 4.12.0 (#253)

See the full diff.

This pull request was created by greenkeeper.io.

_{Tired of seeing this sponsor message? ⚡ greenkeeper upgrade}